Applying the levels of conceptual interoperability model in support of integratability, interoperability, and composability for system-of-systems engineering

The Levels of Conceptual Interoperability Model (LCIM) was developed to cope with the different layers of interoperation of modeling & simulation applications. It introduced technical, syntactic, semantic, pragmatic, dynamic, and conceptual layers of interoperation and showed how they are related to the ideas of integratability, interoperability, and composability. The model was successfully applied in various domains of systems, cybernetics, and informatics

Composable M&S web services for net-centric applications

Service-oriented architectures promise easier integration of functionality in the form of web services into operational systems than is the case with interface-driven system-oriented approaches. Although the Extensible Markup Language (XML) enables a new level of interoperability among heterogeneous systems, XML alone does not solve all interoperability problems users contend with when integrating services into operational systems. To manage the basic challenges of service interoperation, we developed the Levels of Conceptual Interoperability Model (LCIM) to enable a layered approach and gradual solution improvements. Furthermore, we developed methods of model-based data engineering (MBDE) for semantically consistent service integration as a first step. These methods have been applied in the U.S. in collaboration with industry resulting in proofs of concepts. The results are directly applicable in a net-centric and net-enabled environment

An Extended Interoperability Framework for Joint Composability

Interoperation of systems is defined by the aspects of integratability, interoperability, and composability. It is therefore needed, to address all levels of interoperation - from conceptual models via implemented systems to the supported infrastructure - accordingly in an interoperation framework. Several candidates are available and provide valuable part solution. This paper evaluates the Base Object Models (BOMs), Discrete Event Simulation Specifications (DEVS), Unified Language Model (UML) artifacts as used within the Test and Training Enabling Architecture (TENA), the Object-Process Methodology (OPM), and Conceptual Graphs (CG) regarding their contribution. Using the Levels of Conceptual Interoperability Model (LCIM), an extended interoperability framework based on the contributions of BOM, DEVS, UML/TENA, OPM, and CG will be proposed and gaps in support of joint composability are indentified

Exploring Primitives of Meaning in Support of Interoperability

Semantic mismatch between systems is due, in part, to the grouping together of terms who have defined meaning in different levels of granularity, and which are composed together into different groupings by distinct systems. It has been proposed that making use of elemental concepts (referred to here as primitives of meaning) can assist in interoperability, but seeking to define all terms at a level of granularity equal to or greater than that of all involved systems. By decomposing a system’s groups of composed terms into primitives of meaning, the building blocks that can be reassembled into the compositions required by another group (of another system, for instance) can be made apparent. While such a de-composition could serve as the basis for an interoperability enabler, having the decomposition available as a common descriptor to highlight areas of semantic misalignment should prove in itself useful. Taking doctrinal statements for US small unit infantry actions as one semantic system, we show how the elemental ideas that are grouped together into commands can be identified and isolated for reconstruction into other groupings. This is the first research step towards relying on primitives of meaning for interoperability

Software Reuse for Modeling and Simulation

In Modeling and Simulation, as a distinct area of software engineering, there is much interest in being able to reuse software components. However, the practice of simulation development and maintenance is different from software engineering because of several factors. In this paper, a brief overview of the foundations of interoperability, and how they apply to the reuse of model based software is explored, as well as examination of current practices to include M&S software repositories. Some recommendations, based on research at the Virginia Modeling Analysis and Simulation Center (VMASC) and practice at the Raytheon Company Network Centric Services, are made

Applying the Levels of Conceptual Interoperability Model in Support of Integratability, Interoperability, and Composability for System-of-Systems Engineering

The Levels of Conceptual Interoperability Model (LCIM) was developed to cope with the different layers of interoperation of modeling & simulation applications. It introduced technical, syntactic, semantic, pragmatic, dynamic, and conceptual layers of interoperation and showed how they are related to the ideas of integratability, interoperability, and composability. The model was successfully applied in various domains of systems, cybernetics, and informatics

Ontological Implications of the Levels of Conceptual Interoperability Model

The Levels of Conceptual Interoperability Model (LCIM) was developed to cope with the different layers of interoperation of modeling & simulation applications. It introduced technical, syntactic, semantic, pragmatic, dynamic, and conceptual layers of interoperation and showed how they are related to the ideas of integratability, interoperability, and composability. This paper will be presented in the invited session Ontology Driven Interoperability for Agile Applications using Information Systems: Requirements and Applications for Agent Mediated Decision Support at WMSCI 2006

How is M&S Interoperability Different From Other Interoperability Domains?

During every standard workshop or event, the examples of working interoperability solutions are used to motivate for \u27plug and play\u27 standards for M&S as well, like standardized batteries for electronics, or the use of XML to exchange data between heterogeneous systems. While these are successful applications of standards, they are off the mark regarding M&S interoperability. The challenge of M&S is that the product that needs to be made interoperable is not the service or the system alone, but the model behind it as well. The paper shows that the alignment of conceptualizations is the real problem that is not yet dealt with in current interoperability standards

MATHEMATICAL MODELS TOWARDS SELF-ORGANIZING FORMAL FEDERATION LANGUAGES BASED ON CONCEPTUAL MODELS OF INFORMATION EXCHANGE CAPABILITIES

Conceptual models capture information that is crucial for composability of legacy solutions that is not formally captured in the derived technical artifacts. It is necessary to make this information available for the selection (or elimination) of available solutions, their orchestration, and their execution. Current standards barely address this class of problems. The approach presented in this paper is the first step towards self-organizing federation languages. The system interfaces are described in form of exchangeable data. The context of information exchange (syntax, semantics, and pragmatics) is captured as metadata. These metadata are used to identify the elements of a formal federation language that links model composability and simulation interoperability based on conceptual model elements. The paper describes the formal process of selection, orchestration, and execution and the underlying mathematics for the information exchange specifications that bridge conceptual and engineering levels of the federation process.